home *** CD-ROM | disk | FTP | other *** search
/ IRIX Base Documentation 1998 November / IRIX 6.5.2 Base Documentation November 1998.img / usr / share / catman / p_man / cat3 / Xm / XmDisplay.z / XmDisplay
Text File  |  1998-10-30  |  43KB  |  661 lines

  1.  
  2.  
  3.  
  4.      XXXXmmmmDDDDiiiissssppppllllaaaayyyy((((3333XXXX))))             UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV             XXXXmmmmDDDDiiiissssppppllllaaaayyyy((((3333XXXX))))
  5.  
  6.  
  7.  
  8.      NNNNAAAAMMMMEEEE
  9.           XXXXmmmmDDDDiiiissssppppllllaaaayyyy - The Display widget class
  10.  
  11.      SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
  12.           #include <Xm/Display.h>
  13.  
  14.      VVVVEEEERRRRSSSSIIIIOOOONNNN
  15.           This page documents Motif 2.1.
  16.  
  17.      DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
  18.           The XmDisplay object is used by the Motif widgets to store
  19.           information that is specific to a display. It also allows
  20.           the toolkit to access certain information on widget
  21.           hierarchies that would otherwise be unavailable. Each client
  22.           has one XmDisplay object for each display it accesses.
  23.  
  24.           An XmDisplay object is automatically created when the
  25.           application creates the first shell on a display (usually
  26.           accomplished by a call to XXXXttttAAAAppppppppIIIInnnniiiittttiiiiaaaalllliiiizzzzeeee or
  27.           XXXXttttAAAAppppppppCCCCrrrreeeeaaaatttteeeeSSSShhhheeeellllllll).  It is not necessary to create an
  28.           XmDisplay object by any other means.  An application can use
  29.           the function XXXXmmmmGGGGeeeettttXXXXmmmmDDDDiiiissssppppllllaaaayyyy to obtain the widget ID of the
  30.           XmDisplay object for a given display.
  31.  
  32.           An application cannot supply initial values for XmDisplay
  33.           resources as arguments to a call to any function that
  34.           creates widgets.  The application or user can supply initial
  35.           values in a resource file.  After creating the first shell
  36.           on the display, the application can use XXXXmmmmGGGGeeeettttXXXXmmmmDDDDiiiissssppppllllaaaayyyy to
  37.           obtain the widget ID of the XmDisplay object and then call
  38.           XXXXttttSSSSeeeettttVVVVaaaalllluuuueeeessss to set the XmDisplay resources.
  39.  
  40.           XmDisplay resources specify the drag protocol style for a
  41.           client participating in drag and drop transactions. The two
  42.           basic protocol types are preregister and dynamic. When a
  43.           preregister protocol is used, the toolkit handles any
  44.           communication between the initiator and receiver clients and
  45.           displays the appropriate drag-over and drag-under visual
  46.           effects. A client registers its drop sites in advance and
  47.           this information is stored in a property for each top-level
  48.           window. When the drag pointer enters a top-level window, the
  49.           drop site information is read by the initiator. A dynamic
  50.           protocol allows the source and destination clients to
  51.           dynamically communicate drag and drop state information
  52.           between each other, and to update their respective visuals
  53.           accordingly. The toolkit provides drop site information as
  54.           the pointer passes over any given drop site.  In this mode,
  55.           a receiver can supply a procedure to generate its own drag-
  56.           under effects.
  57.  
  58.         CCCCllllaaaasssssssseeeessss
  59.           Display inherits behavior and resources from CCCCoooorrrreeee,
  60.  
  61.  
  62.  
  63.      Page 1                                         (printed 10/24/98)
  64.  
  65.  
  66.  
  67.  
  68.  
  69.  
  70.      XXXXmmmmDDDDiiiissssppppllllaaaayyyy((((3333XXXX))))             UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV             XXXXmmmmDDDDiiiissssppppllllaaaayyyy((((3333XXXX))))
  71.  
  72.  
  73.  
  74.           CCCCoooommmmppppoooossssiiiitttteeee, SSSShhhheeeellllllll, WWWWMMMMSSSShhhheeeellllllll, VVVVeeeennnnddddoooorrrrSSSShhhheeeellllllll, TTTTooooppppLLLLeeeevvvveeeellllSSSShhhheeeellllllll, and
  75.           AAAApppppppplllliiiiccccaaaattttiiiioooonnnnSSSShhhheeeellllllll classes.
  76.  
  77.           The class pointer is _x_m_D_i_s_p_l_a_y_C_l_a_s_s.
  78.  
  79.           The class name is XXXXmmmmDDDDiiiissssppppllllaaaayyyy.
  80.  
  81.         NNNNeeeewwww RRRReeeessssoooouuuurrrrcccceeeessss
  82.           The following table defines a set of widget resources used
  83.           by the programmer to specify data. The programmer can also
  84.           set the resource values for the inherited classes to set
  85.           attributes for this widget.  To reference a resource by name
  86.           or by class in a ....XXXXddddeeeeffffaaaauuuullllttttssss file, remove the XXXXmmmmNNNN or XXXXmmmmCCCC
  87.           prefix and use the remaining letters.  To specify one of the
  88.           defined values for a resource in a ....XXXXddddeeeeffffaaaauuuullllttttssssfile, remove
  89.           the XXXXmmmm prefix and use the remaining letters (in either
  90.           lowercase or uppercase, but include any underscores between
  91.           words). The codes in the access column indicate if the given
  92.           resource can be set at creation time (C), set by using
  93.           XtSetValues (S), retrieved by using XtGetValues (G), or is
  94.           not applicable (N/A).
  95.  
  96.                                                        XXXXmmmmDDDDiiiissssppppllllaaaayyyy RRRReeeessssoooouuuurrrrcccceeee SSSSeeeetttt
  97.           NNNNaaaammmmeeee                            CCCCllllaaaassssssss                           TTTTyyyyppppeeee             DDDDeeeeffffaaaauuuulllltttt                  AAAAcccccccceeeessssssss
  98.           XmNdefaultButtonEmphasis        XmCDefaultButtonEmphasis        XtEnum           XmEXTERNAL_HIGHLIGHT     C
  99.           XmNdefaultVirtualBindings       XmCDefaultVirtualBindings       String           dynamic                  C
  100.           XmNdragInitiatorProtocolStyle   XmCDragInitiatorProtocolStyle   unsigned char    XmDRAG_PREFER_RECEIVER   CG
  101.           XmNdragReceiverProtocolStyle    XmCDragReceiverProtocolStyle    unsigned char    XmDRAG_PREFER_DYNAMIC    CG
  102.           XmNdragStartCallback            XmCCallback                     XtCallbackList   NULL                     C
  103.           XmNenableBtn1Transfer           XmCEnableBtn1Transfer           XtEnum           XmOFF                    C
  104.           XmNenableButtonTab              XmCEnableButtonTab              Boolean          False                    C
  105.           XmNenableDragIcon               XmCEnableDragIcon               Boolean          False                    C
  106.           XmNenableEtchedInMenu           XmCEnableEtchedInMenu           Boolean          False                    C
  107.           XmNenableToggleColor            XmCEnableToggleColor            Boolean          False                    C
  108.           XmNenableToggleVisual           XmCEnableToggleVisual           Boolean          False                    C
  109.           XmNenableUnselectableDrag       XmCEnableUnselectableDrag       Boolean          True                     C
  110.           XmNenableWarp                   XmCEnableWarp                   XtEnum           True                     CSG
  111.           XmNmotifVersion                 XmCMotifVersion                 int              XmVERSION                CSG
  112.           XmNnoFontCallback               XmCCallback                     XtCallbackList   NULL                     C
  113.           XmNnoRenditionCallback          XmCCallback                     XtCallbackList   NULL                     C
  114.           XmNuserData                     XmCUserData                     XtPointer        NULL                     CSG
  115.  
  116.           XXXXmmmmNNNNddddeeeeffffaaaauuuullllttttBBBBuuuuttttttttoooonnnnEEEEmmmmpppphhhhaaaassssiiiissss
  117.                     Specifies whether to change the look of the
  118.                     PushButton widget and gadget that have the
  119.                     XXXXmmmmNNNNsssshhhhoooowwwwAAAAssssDDDDeeeeffffaaaauuuulllltttt resource set. When the PushButton
  120.                     is the default, it has an etched out button which
  121.                     is enclosed with another etched in border. The
  122.                     XXXXmmmmNNNNddddeeeeffffaaaauuuullllttttBBBBuuuuttttttttoooonnnnEEEEmmmmpppphhhhaaaassssiiiissss has the follow possible
  123.                     values, which affect the location cursor:
  124.  
  125.                     XXXXmmmmIIIINNNNTTTTEEEERRRRNNNNAAAALLLL____HHHHIIIIGGGGHHHHLLLLIIIIGGGGHHHHTTTT
  126.  
  127.  
  128.  
  129.      Page 2                                         (printed 10/24/98)
  130.  
  131.  
  132.  
  133.  
  134.  
  135.  
  136.      XXXXmmmmDDDDiiiissssppppllllaaaayyyy((((3333XXXX))))             UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV             XXXXmmmmDDDDiiiissssppppllllaaaayyyy((((3333XXXX))))
  137.  
  138.  
  139.  
  140.                               Causes the location cursor to appear in
  141.                               between the two etched borders to
  142.                               minimize the space required.
  143.  
  144.                     XXXXmmmmEEEEXXXXTTTTEEEERRRRNNNNAAAALLLL____HHHHIIIIGGGGHHHHLLLLIIIIGGGGHHHHTTTT
  145.                               Causes the PushButton to draw the
  146.                               location cursor outside the second
  147.                               border.
  148.  
  149.           XXXXmmmmNNNNddddeeeeffffaaaauuuullllttttVVVViiiirrrrttttuuuuaaaallllBBBBiiiinnnnddddiiiinnnnggggssss
  150.                     Specifies the default virtual bindings for the
  151.                     display.  Following is an example of a
  152.                     specification for the ddddeeeeffffaaaauuuullllttttVVVViiiirrrrttttuuuuaaaallllBBBBiiiinnnnddddiiiinnnnggggssss
  153.                     resource in a resource file:
  154.  
  155.           *defaultVirtualBindings: \
  156.                   osfBackSpace:       <Key>BackSpace       \n\
  157.                   osfInsert:       <Key>InsertChar      \n\
  158.                   osfDelete:       <Key>DeleteChar      \n\
  159.                   ...
  160.                   osfLeft:       <Key>left, Ctrl<Key>H
  161.  
  162.           XXXXmmmmNNNNddddrrrraaaaggggIIIInnnniiiittttiiiiaaaattttoooorrrrPPPPrrrroooottttooooccccoooollllSSSSttttyyyylllleeee
  163.                     Specifies the drag and drop protocol requirements
  164.                     or preference when the client is an initiator. The
  165.                     possible values are
  166.  
  167.                     XXXXmmmmDDDDRRRRAAAAGGGG____PPPPRRRREEEERRRREEEEGGGGIIIISSSSTTTTEEEERRRR
  168.                               As an initiator, this client does not
  169.                               use the dynamic protocol and can only
  170.                               arrange visual effects with receivers
  171.                               who provide preregistered information.
  172.  
  173.                     XXXXmmmmDDDDRRRRAAAAGGGG____DDDDYYYYNNNNAAAAMMMMIIIICCCC
  174.                               As an initiator, this client does not
  175.                               make use of any preregistered drop site
  176.                               information made available by other
  177.                               clients, and can only arrange visual
  178.                               effects with receivers who use the
  179.                               dynamic protocol.
  180.  
  181.                     XXXXmmmmDDDDRRRRAAAAGGGG____NNNNOOOONNNNEEEE
  182.                               Specifies that drag and drop is disabled
  183.                               for this client.
  184.  
  185.                     XXXXmmmmDDDDRRRRAAAAGGGG____DDDDRRRROOOOPPPP____OOOONNNNLLLLYYYY
  186.                               As an initiator, this client does not
  187.                               use either the preregistered drop site
  188.                               information or the dynamic protocol. It
  189.                               supports dragging, and any time the
  190.                               cursor is over a client that supports
  191.                               drag and drop, valid feedback is
  192.  
  193.  
  194.  
  195.      Page 3                                         (printed 10/24/98)
  196.  
  197.  
  198.  
  199.  
  200.  
  201.  
  202.      XXXXmmmmDDDDiiiissssppppllllaaaayyyy((((3333XXXX))))             UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV             XXXXmmmmDDDDiiiissssppppllllaaaayyyy((((3333XXXX))))
  203.  
  204.  
  205.  
  206.                               provided. There are no other visual
  207.                               effects.
  208.  
  209.                     XXXXmmmmDDDDRRRRAAAAGGGG____PPPPRRRREEEEFFFFEEEERRRR____DDDDYYYYNNNNAAAAMMMMIIIICCCC
  210.                               As an initiator, this client can support
  211.                               both the preregister and dynamic
  212.                               protocols, but prefers to use dynamic
  213.                               protocols whenever possible in order to
  214.                               provide high-quality drag-under
  215.                               feedback.
  216.  
  217.                     XXXXmmmmDDDDRRRRAAAAGGGG____PPPPRRRREEEEFFFFEEEERRRR____PPPPRRRREEEERRRREEEEGGGGIIIISSSSTTTTEEEERRRR
  218.                               As an initiator, this client can support
  219.                               both the preregister and dynamic
  220.                               protocols, but prefers to use the
  221.                               preregister protocol whenever possible
  222.                               in order to accommodate performance
  223.                               needs or to provide consistent drag-over
  224.                               feedback.
  225.  
  226.                     XXXXmmmmDDDDRRRRAAAAGGGG____PPPPRRRREEEEFFFFEEEERRRR____RRRREEEECCCCEEEEIIIIVVVVEEEERRRR
  227.                               Indicates that this client can support
  228.                               both preregister and dynamic protocols,
  229.                               but will defer to the preference of the
  230.                               receiver client.  This value is valid
  231.                               only for the
  232.                               XXXXmmmmNNNNddddrrrraaaaggggIIIInnnniiiittttiiiiaaaattttoooorrrrPPPPrrrroooottttooooccccoooollllSSSSttttyyyylllleeeeresource,
  233.                               and is its default value.
  234.  
  235.           XXXXmmmmNNNNddddrrrraaaaggggRRRReeeecccceeeeiiiivvvveeeerrrrPPPPrrrroooottttooooccccoooollllSSSSttttyyyylllleeee
  236.                     Specifies the drag and drop protocol requirements
  237.                     or preference when this client is a receiver. The
  238.                     values are
  239.  
  240.                     XXXXmmmmDDDDRRRRAAAAGGGG____PPPPRRRREEEERRRREEEEGGGGIIIISSSSTTTTEEEERRRR
  241.                               As a receiver, this client preregisters
  242.                               drop site information and does not use
  243.                               the dynamic protocol. It can only
  244.                               arrange visual effects with initiators
  245.                               who make use of the preregistered
  246.                               information.
  247.  
  248.                     XXXXmmmmDDDDRRRRAAAAGGGG____DDDDYYYYNNNNAAAAMMMMIIIICCCC
  249.                               As a receiver, this client uses the
  250.                               dynamic protocol and does not
  251.                               preregister drop site information. It
  252.                               can only arrange visual effects with
  253.                               initiators who use the dynamic protocol.
  254.  
  255.                     XXXXmmmmDDDDRRRRAAAAGGGG____NNNNOOOONNNNEEEE
  256.                               Specifies that drag and drop is disabled
  257.                               for this client.
  258.  
  259.  
  260.  
  261.      Page 4                                         (printed 10/24/98)
  262.  
  263.  
  264.  
  265.  
  266.  
  267.  
  268.      XXXXmmmmDDDDiiiissssppppllllaaaayyyy((((3333XXXX))))             UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV             XXXXmmmmDDDDiiiissssppppllllaaaayyyy((((3333XXXX))))
  269.  
  270.  
  271.  
  272.                     XXXXmmmmDDDDRRRRAAAAGGGG____DDDDRRRROOOOPPPP____OOOONNNNLLLLYYYY
  273.                               As a receiver, this client neither uses
  274.                               the dynamic protocol nor preregisters
  275.                               drop site information. It supports
  276.                               dropping, and when dragging over this
  277.                               client, valid feedback is always
  278.                               provided, but there are no other visual
  279.                               effects.
  280.  
  281.                     XXXXmmmmDDDDRRRRAAAAGGGG____PPPPRRRREEEEFFFFEEEERRRR____DDDDYYYYNNNNAAAAMMMMIIIICCCC
  282.                               As a receiver, this client can support
  283.                               both the preregister and dynamic
  284.                               protocols, but prefers to use the
  285.                               dynamic protocol whenever possible in
  286.                               order to provide high-quality drag-under
  287.                               feedback.
  288.  
  289.                     XXXXmmmmDDDDRRRRAAAAGGGG____PPPPRRRREEEEFFFFEEEERRRR____PPPPRRRREEEERRRREEEEGGGGIIIISSSSTTTTEEEERRRR
  290.                               As a receiver, this client can support
  291.                               both the preregister and dynamic
  292.                               protocols, but prefers to use the
  293.                               preregister protocol whenever possible
  294.                               in order to accommodate performance
  295.                               needs.
  296.  
  297.                     The default value of this resource is dependent on
  298.                     the capabilities of the display. If the display
  299.                     supports the shape extension, allowing the dynamic
  300.                     protocol to use arbitrarily sized drag cursors,
  301.                     the default of this resource is
  302.                     XXXXmmmmDDDDRRRRAAAAGGGG____PPPPRRRREEEEFFFFEEEERRRR____DDDDYYYYNNNNAAAAMMMMIIIICCCC, otherwise the default is
  303.                     XXXXmmmmDDDDRRRRAAAAGGGG____PPPPRRRREEEEFFFFEEEERRRR____PPPPRRRREEEERRRREEEEGGGGIIIISSSSTTTTEEEERRRR.
  304.  
  305.                     The actual protocol used between an initiator and
  306.                     a receiver is based on the protocol style of the
  307.                     receiver and initiator. The decision matrix is
  308.                     described in the following table.
  309.  
  310.                                      DDDDrrrraaaagggg RRRReeeecccceeeeiiiivvvveeeerrrr PPPPrrrroooottttooooccccoooollll SSSSttttyyyylllleeee
  311.                                      PPPPrrrreeeerrrreeeeggggiiiisssstttteeeerrrr                    PPPPrrrreeeeffffeeeerrrr PPPPrrrreeeerrrreeeeggggiiiisssstttteeeerrrr   PPPPrrrreeeeffffeeeerrrr DDDDyyyynnnnaaaammmmiiiicccc   DDDDyyyynnnnaaaammmmiiiicccc
  312.                                      Preregister                    Preregister          Preregister      Drop Only
  313.                     DDDDrrrraaaagggg IIIInnnniiiittttiiiiaaaattttoooorrrr   Preregister                    Preregister          Preregister      Dynamic
  314.                                      Preregister                    Preregister          Dynamic          Dynamic
  315.                                      Preregister                    Dynamic              Dynamic          Dynamic
  316.                                      DDDDrrrroooopppp OOOOnnnnllllyyyy                      DDDDyyyynnnnaaaammmmiiiicccc              DDDDyyyynnnnaaaammmmiiiicccc          DDDDyyyynnnnaaaammmmiiiicccc
  317.  
  318.                     The value XXXXmmmmDDDDRRRRAAAAGGGG____NNNNOOOONNNNEEEE does not appear in the
  319.                     matrix. When specified for either the initiator or
  320.                     receiver side, XXXXmmmmDDDDRRRRAAAAGGGG____NNNNOOOONNNNEEEE implies that drag and
  321.                     drop transactions are not supported. A value of
  322.                     XXXXmmmmDDDDRRRRAAAAGGGG____DDDDRRRROOOOPPPP____OOOONNNNLLLLYYYY (Drop Only) results when an
  323.                     initiator and receiver cannot compromise protocol
  324.  
  325.  
  326.  
  327.      Page 5                                         (printed 10/24/98)
  328.  
  329.  
  330.  
  331.  
  332.  
  333.  
  334.      XXXXmmmmDDDDiiiissssppppllllaaaayyyy((((3333XXXX))))             UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV             XXXXmmmmDDDDiiiissssppppllllaaaayyyy((((3333XXXX))))
  335.  
  336.  
  337.  
  338.                     styles, that is, one client requires dynamic mode
  339.                     while the other can only support preregister mode,
  340.                     or if either explicitly has specified
  341.                     XXXXmmmmDDDDRRRRAAAAGGGG____DDDDRRRROOOOPPPP____OOOONNNNLLLLYYYY.
  342.  
  343.           XXXXmmmmNNNNddddrrrraaaaggggSSSSttttaaaarrrrttttCCCCaaaallllllllbbbbaaaacccckkkk
  344.                     Specifies the list of callbacks that are invoked
  345.                     when the XXXXmmmmDDDDrrrraaaaggggSSSSttttaaaarrrrtttt function is called. The type
  346.                     of structure whose address is passed to this
  347.                     callback is XXXXmmmmDDDDrrrraaaaggggSSSSttttaaaarrrrttttCCCCaaaallllllllbbbbaaaacccckkkkSSSSttttrrrruuuucccctttt.  The
  348.                     callback reason is XXXXmmmmCCCCRRRR____DDDDRRRRAAAAGGGG____SSSSTTTTAAAARRRRTTTT.
  349.  
  350.           XXXXmmmmNNNNeeeennnnaaaabbbblllleeeeBBBBttttnnnn1111TTTTrrrraaaannnnssssffffeeeerrrr
  351.                     Specifies if selection and transfer actions are
  352.                     integrated on Btn1 and extend actions are
  353.                     activated on Btn2. This resource can take the
  354.                     following values:
  355.  
  356.                     XXXXmmmmOOOOFFFFFFFF     Disables integration and selection
  357.                               activation on Btn1.
  358.  
  359.                     _X_m_B_U_T_T_O_N_2__T_R_A_N_S_F_E_R
  360.                               Enables integration and selection
  361.                               activation on Btn1 and transfer on Btn2.
  362.  
  363.                     _X_m_B_U_T_T_O_N_2__A_D_J_U_S_T
  364.                               Enables integration and selection
  365.                               activation on Btn1 and adjust on Btn2.
  366.  
  367.                     This resource affects the actions of Text,
  368.                     TextField, List, and Container.
  369.  
  370.           XXXXmmmmNNNNeeeennnnaaaabbbblllleeeeBBBBuuuuttttttttoooonnnnTTTTaaaabbbb
  371.                     Specifies if the action for the <<<<TTTTaaaabbbb>>>> key
  372.                     (KKKKNNNNeeeexxxxttttFFFFiiiieeeelllldddd and KKKKPPPPrrrreeeevvvvFFFFiiiieeeelllldddd actions) is to be
  373.                     modified.  A value of True modifies the key to
  374.                     move as an arrow key until the boundary of a tab
  375.                     group is reached. Then, at the boundary of the tab
  376.                     group, KKKKNNNNeeeexxxxttttFFFFiiiieeeelllldddd and KKKKPPPPrrrreeeevvvvFFFFiiiieeeelllldddd will move to the
  377.                     next or previous tab group, respectively. A value
  378.                     of False does not cause modification.
  379.  
  380.           XXXXmmmmNNNNeeeennnnaaaabbbblllleeeeDDDDrrrraaaaggggIIIIccccoooonnnn
  381.                     Specifies which set of icons are to be used for
  382.                     system default cursors during drag and drop
  383.                     operations. A value of False specifies that
  384.                     earlier versions of Motif release icons are used,
  385.                     a value of True specifies that alternate icons are
  386.                     used. This resource affects both the 16x16 and the
  387.                     32x32 icons that the system defaults for each of
  388.                     the Screen objects associated with this display.
  389.  
  390.  
  391.  
  392.  
  393.      Page 6                                         (printed 10/24/98)
  394.  
  395.  
  396.  
  397.  
  398.  
  399.  
  400.      XXXXmmmmDDDDiiiissssppppllllaaaayyyy((((3333XXXX))))             UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV             XXXXmmmmDDDDiiiissssppppllllaaaayyyy((((3333XXXX))))
  401.  
  402.  
  403.  
  404.           XXXXmmmmNNNNeeeennnnaaaabbbblllleeeeEEEEttttcccchhhheeeeddddIIIInnnnMMMMeeeennnnuuuu
  405.                     Specifies the shadowing of the button widgets and
  406.                     gadgets in menus when the control is activated. A
  407.                     value of True causes the selected menu to be drawn
  408.                     with the shadow etched in; this shadow style is
  409.                     consistent with the selected appearance of other
  410.                     button widgets outside of menus. A value of False
  411.                     causes the selected menu to be draw with the
  412.                     shadow etched out. This resource affects the
  413.                     actions of PushButton, ToggleButton, and
  414.                     CascadeButton widgets and gadgets when they are
  415.                     children of Menu.
  416.  
  417.                     When this resource is set, the background of a
  418.                     button in a menu uses the XXXXmmmmNNNNsssseeeelllleeeeccccttttCCCCoooolllloooorrrr(derived
  419.                     from the XXXXmmmmNNNNsssseeeelllleeeeccccttttPPPPiiiixxxxeeeellll) when armed as a default.
  420.                     A PPPPuuuusssshhhhBBBBuuuuttttttttoooonnnnuses the XXXXmmmmNNNNaaaarrrrmmmmCCCCoooolllloooorrrrif it is defined.
  421.                     A TTTToooogggggggglllleeeeBBBBuuuuttttttttoooonnnnuses the XXXXmmmmNNNNsssseeeelllleeeeccccttttCCCCoooolllloooorrrrif
  422.                     XXXXmmmmNNNNiiiinnnnddddiiiiccccaaaattttoooorrrrOOOOnnnnis FFFFaaaallllsssseeee and XXXXmmmmNNNNffffiiiillllllllOOOOnnnnSSSSeeeelllleeeeccccttttis TTTTrrrruuuueeee.
  423.  
  424.           XXXXmmmmNNNNeeeennnnaaaabbbblllleeeeTTTToooogggggggglllleeeeCCCCoooolllloooorrrr
  425.                     Specifies how to determine the default value of
  426.                     the XXXXmmmmNNNNsssseeeelllleeeeccccttttCCCCoooolllloooorrrr resource of ToggleButton and
  427.                     ToggleButtonGadget.  A value of True causes the
  428.                     default value of XXXXmmmmNNNNsssseeeelllleeeeccccttttCCCCoooolllloooorrrrto be set to the
  429.                     value of XXXXmmmmNNNNhhhhiiiigggghhhhlllliiiigggghhhhttttCCCCoooolllloooorrrr.  A value of False
  430.                     causes the default value of XXXXmmmmNNNNsssseeeelllleeeeccccttttCCCCoooolllloooorrrrto be
  431.                     set to the value of XXXXmmmmNNNNbbbbaaaacccckkkkggggrrrroooouuuunnnndddd.  This resource
  432.                     only affects the appearance of ToggleButton
  433.                     widgets and gadgets that are in XXXXmmmmOOOONNNNEEEE____OOOOFFFF____MMMMAAAANNNNYYYY or
  434.                     XXXXmmmmOOOONNNNEEEE____OOOOFFFF____MMMMAAAANNNNYYYY____RRRROOOOUUUUNNNNDDDD mode. In addition,
  435.                     XXXXmmmmNNNNeeeennnnaaaabbbblllleeeeTTTToooogggggggglllleeeeCCCCoooolllloooorrrronly influences the default
  436.                     value of XXXXmmmmNNNNsssseeeelllleeeeccccttttCCCCoooolllloooorrrr. That is, if the user or
  437.                     application sets a value for XXXXmmmmNNNNsssseeeelllleeeeccccttttCCCCoooolllloooorrrr, then
  438.                     XXXXmmmmNNNNeeeennnnaaaabbbblllleeeeTTTToooogggggggglllleeeeCCCCoooolllloooorrrr is ignored.
  439.  
  440.           XXXXmmmmNNNNeeeennnnaaaabbbblllleeeeTTTToooogggggggglllleeeeVVVViiiissssuuuuaaaallll
  441.                     Specifies the visual appearance of the
  442.                     ToggleButton widget and/or gadget. This resource
  443.                     affects the default value of the
  444.                     ToggleButton[Gadget] XXXXmmmmNNNNiiiinnnnddddiiiiccccaaaattttoooorrrrTTTTyyyyppppeeee and
  445.                     XXXXmmmmNNNNiiiinnnnddddiiiiccccaaaattttoooorrrrOOOOnnnn resources. When the ToggleButton is
  446.                     in a RadioBox, a value of True causes the
  447.                     XXXXmmmmOOOONNNNEEEE____OOOOFFFF____MMMMAAAANNNNYYYY____RRRROOOOUUUUNNNNDDDD (a shadowed circle) to be the
  448.                     default.  Otherwise, when this resource is True,
  449.                     the ToggleButton XXXXmmmmNNNNiiiinnnnddddiiiiccccaaaattttoooorrrrOOOOnnnn resource causes a
  450.                     default of XXXXmmmmNNNN____OOOOFFFF____MMMMAAAANNNNYYYY, which will be a shadowed
  451.                     square with a check mark (check box).
  452.  
  453.                     A value of False causes the following:
  454.  
  455.                     XXXXmmmmOOOONNNNEEEE____OOOOFFFF____MMMMAAAANNNNYYYY
  456.  
  457.  
  458.  
  459.      Page 7                                         (printed 10/24/98)
  460.  
  461.  
  462.  
  463.  
  464.  
  465.  
  466.      XXXXmmmmDDDDiiiissssppppllllaaaayyyy((((3333XXXX))))             UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV             XXXXmmmmDDDDiiiissssppppllllaaaayyyy((((3333XXXX))))
  467.  
  468.  
  469.  
  470.                               Is a shadowed diamond.
  471.  
  472.                     XXXXmmmmNNNN____OOOOFFFF____MMMMAAAANNNNYYYY
  473.                               Is a shadowed square.
  474.  
  475.           XXXXmmmmNNNNeeeennnnaaaabbbblllleeeeUUUUnnnnsssseeeelllleeeeccccttttaaaabbbblllleeeeDDDDrrrraaaagggg
  476.                     Specifies whether or not it is possible to drag
  477.                     from Label and Scale.  A value of True enables the
  478.                     drag; a value of False disables it.
  479.  
  480.           XXXXmmmmNNNNeeeennnnaaaabbbblllleeeeWWWWaaaarrrrpppp
  481.                     Specifies if an application is allowed to warp the
  482.                     pointer from the user. A value of True enables
  483.                     warping, a value of False does not.
  484.  
  485.           XXXXmmmmNNNNmmmmoooottttiiiiffffVVVVeeeerrrrssssiiiioooonnnn
  486.                     Specifies the current version of Motif that the
  487.                     current implementation is supposed to behave like.
  488.                     By default, this resource gets its value from
  489.                     release values in XXXXmmmm....hhhh.
  490.  
  491.           XXXXmmmmNNNNnnnnooooFFFFoooonnnnttttCCCCaaaallllllllbbbbaaaacccckkkk
  492.                     This callback is called whenever a rendition
  493.                     attempts to load a font or fontset and fails. This
  494.                     can happen on creation if the font is specified as
  495.                     XXXXmmmmLLLLOOOOAAAADDDD____IIIIMMMMMMMMEEEEDDDDIIIIAAAATTTTEEEE or when an attempt is made to
  496.                     render an XXXXmmmmSSSSttttrrrriiiinnnngggg using a font specified as
  497.                     XXXXmmmmLLLLOOOOAAAADDDD____DDDDEEEEFFFFEEEERRRRRRRREEEEDDDD. An application can have this
  498.                     callback attempt to remedy this problem by calling
  499.                     XXXXmmmmRRRReeeennnnddddiiiittttiiiioooonnnnUUUUppppddddaaaatttteeee on the input rendition to
  500.                     provide a font for the widget to use. This may be
  501.                     done by either providing an an alternative font
  502.                     name to be loaded using the XXXXmmmmNNNNffffoooonnnnttttNNNNaaaammmmeeee and
  503.                     XXXXmmmmNNNNffffoooonnnnttttTTTTyyyyppppeeee resources or with an already loaded
  504.                     font using the XXXXmmmmNNNNffffoooonnnntttt resource. The callback
  505.                     reason is XXXXmmmmCCCCRRRR____NNNNOOOO____FFFFOOOONNNNTTTT. This callback uses the
  506.                     XXXXmmmmDDDDiiiissssppppllllaaaayyyyCCCCaaaallllllllbbbbaaaacccckkkkSSSSttttrrrruuuucccctttt structure.
  507.  
  508.           XXXXmmmmNNNNnnnnooooRRRReeeennnnddddiiiittttiiiioooonnnnCCCCaaaallllllllbbbbaaaacccckkkk
  509.                     This callback is called whenever an attempt is
  510.                     made to render a segment with a _R_E_N_D_I_T_I_O_N tag
  511.                     which does not match any renditions in a given
  512.                     render table. The callback reason is
  513.                     XXXXmmmmCCCCRRRR____NNNNOOOO____RRRREEEENNNNDDDDIIIITTTTIIIIOOOONNNN. This callback uses the
  514.                     XXXXmmmmDDDDiiiissssppppllllaaaayyyyCCCCaaaallllllllbbbbaaaacccckkkkSSSSttttrrrruuuucccctttt structure.
  515.  
  516.                     An application can have this callback attempt to
  517.                     remedy this problem by creating a new rendition
  518.                     with the given tag and adding it to rrrreeeennnnddddeeeerrrr____ttttaaaabbbblllleeee.
  519.  
  520.                     The XXXXmmmmNNNNnnnnooooRRRReeeennnnddddiiiittttiiiioooonnnnCCCCaaaallllllllbbbbaaaacccckkkk should deallocate the
  521.                     render table passed in in the rrrreeeennnnddddeeeerrrr____ttttaaaabbbblllleeee field
  522.  
  523.  
  524.  
  525.      Page 8                                         (printed 10/24/98)
  526.  
  527.  
  528.  
  529.  
  530.  
  531.  
  532.      XXXXmmmmDDDDiiiissssppppllllaaaayyyy((((3333XXXX))))             UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV             XXXXmmmmDDDDiiiissssppppllllaaaayyyy((((3333XXXX))))
  533.  
  534.  
  535.  
  536.                     of the callback structure. Note that the table
  537.                     will automatically be deallocated if the
  538.                     XXXXmmmmRRRReeeennnnddddeeeerrrrTTTTaaaabbbblllleeeeAAAAddddddddRRRReeeennnnddddiiiittttiiiioooonnnnssss function is called on
  539.                     it. The callback should NOT deallocate the
  540.                     modified render table that is passed back to Motif
  541.                     in the rrrreeeennnnddddeeeerrrr____ttttaaaabbbblllleeeefield. If the application
  542.                     wishes to manipulate this render table further, it
  543.                     should make a copy with the XXXXmmmmRRRReeeennnnddddeeeerrrrTTTTaaaabbbblllleeeeCCCCooooppppyyyy
  544.                     function before returning from the callback.
  545.  
  546.           XXXXmmmmNNNNuuuusssseeeerrrrDDDDaaaattttaaaa
  547.                     Specifies a client data pointer for applications.
  548.                     An internally unused resource.
  549.  
  550.         IIIInnnnhhhheeeerrrriiiitttteeeedddd RRRReeeessssoooouuuurrrrcccceeeessss
  551.           All of the superclass resources inherited by XmDisplay are
  552.           designated N/A (not applicable).
  553.  
  554.         CCCCaaaallllllllbbbbaaaacccckkkk IIIInnnnffffoooorrrrmmmmaaaattttiiiioooonnnn
  555.           A pointer to the following structure is passed to the
  556.           XXXXmmmmNNNNddddrrrraaaaggggSSSSttttaaaarrrrttttCCCCaaaallllllllbbbbaaaacccckkkk callback:
  557.  
  558.           typedef struct
  559.           {
  560.                   int _r_e_a_s_o_n;
  561.                   XEvent  *_e_v_e_n_t;
  562.                   Widget _t_i_m_e_S_t_a_m_p;
  563.                   Boolean _d_o_i_t;
  564.           }XmDragStartCallbackStruct;
  565.  
  566.           _r_e_a_s_o_n    Indicates why the callback was invoked
  567.  
  568.           _e_v_e_n_t     Points to the _X_E_v_e_n_t that triggered the callback
  569.  
  570.           _w_i_d_g_e_t    Indicates the ID of the widget from which the drag
  571.                     was initiated.
  572.  
  573.           _d_o_i_t      Is an IN/OUT member that allows the callback to
  574.                     determine whether to continue with the drag or
  575.                     cancel. Setting _d_o_i_t to False will cancel the
  576.                     drag. The default value is NULL.
  577.  
  578.           A pointer to the following structure is passed to the
  579.           XXXXmmmmNNNNnnnnooooFFFFoooonnnnttttCCCCaaaallllllllbbbbaaaacccckkkk and XXXXmmmmNNNNnnnnooooRRRReeeennnnddddiiiittttiiiioooonnnnCCCCaaaallllllllbbbbaaaacccckkkk callbacks:
  580.  
  581.           typedef struct
  582.           {
  583.                   int _r_e_a_s_o_n;
  584.                   XEvent *_e_v_e_n_t;
  585.                   XmRendition _r_e_n_d_i_t_i_o_n;
  586.                   char *_f_o_n_t__n_a_m_e;
  587.                   XmRenderTable _r_e_n_d_e_r__t_a_b_l_e;
  588.  
  589.  
  590.  
  591.      Page 9                                         (printed 10/24/98)
  592.  
  593.  
  594.  
  595.  
  596.  
  597.  
  598.      XXXXmmmmDDDDiiiissssppppllllaaaayyyy((((3333XXXX))))             UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV             XXXXmmmmDDDDiiiissssppppllllaaaayyyy((((3333XXXX))))
  599.  
  600.  
  601.  
  602.                   XmStringTag _t_a_g;
  603.           }XmDisplayCallbackStruct;
  604.  
  605.           _r_e_a_s_o_n    Indicates why the callback was invoked.
  606.  
  607.           _e_v_e_n_t     Points to the _X_E_v_e_n_t that triggered the callback.
  608.                     It can be NULL.
  609.  
  610.           _r_e_n_d_i_t_i_o_n Specifies the rendition with the missing font.
  611.  
  612.           _f_o_n_t__n_a_m_e Specifies the name of the font or font set which
  613.                     could not be loaded.
  614.  
  615.           rrrreeeennnnddddeeeerrrr____ttttaaaabbbblllleeee
  616.                     Specifies the render table with the missing
  617.                     rendition.
  618.  
  619.           _t_a_g       Specifies the tag of the missing rendition.
  620.  
  621.           The following table describes the reasons for which the
  622.           individual callback structure fields are valid.
  623.           RRRReeeeaaaassssoooonnnn              VVVVaaaalllliiiidddd FFFFiiiieeeellllddddssss
  624.           XmCR_NO_FONT        _r_e_n_d_i_t_i_o_n, _f_o_n_t__n_a_m_e
  625.           XmCR_NO_RENDITION   _r_e_n_d_e_r__t_a_b_l_e, _t_a_g
  626.  
  627.      RRRREEEELLLLAAAATTTTEEEEDDDD
  628.           AAAApppppppplllliiiiccccaaaattttiiiioooonnnnSSSShhhheeeellllllll(3), CCCCoooommmmppppoooossssiiiitttteeee(3), CCCCoooorrrreeee(3),
  629.           TTTTooooppppLLLLeeeevvvveeeellllSSSShhhheeeellllllll(3), VVVVeeeennnnddddoooorrrrSSSShhhheeeellllllll(3), WWWWMMMMSSSShhhheeeellllllll(3),
  630.           XXXXmmmmGGGGeeeettttXXXXmmmmDDDDiiiissssppppllllaaaayyyy(3), and XXXXmmmmSSSSccccrrrreeeeeeeennnn(3).
  631.  
  632.  
  633.  
  634.  
  635.  
  636.  
  637.  
  638.  
  639.  
  640.  
  641.  
  642.  
  643.  
  644.  
  645.  
  646.  
  647.  
  648.  
  649.  
  650.  
  651.  
  652.  
  653.  
  654.  
  655.  
  656.  
  657.      Page 10                                        (printed 10/24/98)
  658.  
  659.  
  660.  
  661.